home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Libris Britannia 4
/
science library(b).zip
/
science library(b)
/
COMMUNIC
/
1024.ZIP
/
GTCTL.DOC
< prev
next >
Wrap
Text File
|
1987-08-16
|
39KB
|
658 lines
GTCTL Release 5.2
GT PowerComm Sysop Control Program
15 August 1987
Copyright (1987) James R. Davis
All rights reserved
This program and its documentation are a companion to the software and
documentation created by P&M Software Co. known as GT PowerComm.
Collectively these programs (along with GTLOG) provide the user an
extremely powerful yet relatively easy to use communication system for
use on an IBM or compatible micro-computer system. All of these
products by P&M Software and James R. Davis are provided in the form of
Shareware and made available through electronic Bulletin Boards located
all over the country. As such, you have the right to use these products
and to freely copy and distribute them, provided only that the copies
include both code and documentation, unmodified, and that only the
authoring company may sell the programs and documentation for a profit.
It is not necessary to register for GTCTL or GTLOG separately from GT
PowerComm. Further, there is not a separate registration fee for them.
It is strongly suggested, however, if you find the set of programs to be
useful, that you register your copy of GT with P&M Software Co. and that
you accompany your registration with the currently valid fee requested.
This is the only way to insure the continued availability and support of
such quality software.
A registration form is included as the last page of this documentation.
The authors of GT PowerComm and the companion series of support programs
sincerely hope you will find these programs to be the finest examples of
communications capabilities available anywhere and that you will benefit
from their use.
Please note, the authors advise you that they have no responsiblity for
consequential damages, whatever.
James R. Davis
2010 Woodland Springs
Houston, Texas 77077
(713) 497-2306 Data
(713) 558-5015 Voice
1
GTCTL - brief summary
This program provides the user of GT PowerComm with support functions
that facilitate the maintenance of the Host mode of that fine program.
In the Host mode of GT PowerComm you are able to provide unattended
access to your system to a controlled set of remote users. You are able
to specify what functions those users are able to perform, the amount of
time each is allowed to access the system, which users are NOT allowed
access, and to maintain a complete log of system activity as well as a
complete general and private message data base for the user community.
Obviously, with the flexibility the Host mode provides, you, as the
System Operator (Sysop), must assume some new responsibilities. For
example, the message data base could grow without end if you did not
have a way to control its size. Certain callers of your system may call
only once and never call back. In that case you may want to purge that
user's name from those who are currently active and authorized. Certain
callers into your system will be undesirable for various reasons and you
may want to preemptively prevent them from logging on to the system.
After a period of time you may want to renumber the messages in the data
base. And, you may simply wish to determine which of your callers are
currently using that message data base or which currently have
unreceived mail waiting for them in that data base.
These are the kinds of functions that GTCTL was written to support. The
other companion program to GT PowerComm is called GTLOG which is used to
determine who has sent you files, who has received certain files from
your system, the performance of your system's file transfer functions,
telephone expense estimates, the reading of Sysop private messages or
file Upload descriptions, and several other file activity analyses
functions.
GTCTL is a stand alone program that assumes only that you have installed
the ANSI.SYS driver (or equivalent) in your system. It finds all files
automatically by searching your environment for the GTPATH name and, if
it finds that name, allows you to run the program from any directory on
your disk. If you have not specified the GTPATH name in your
environment then GTCTL must be run from within the directory which
contains the GT PowerComm files (Typically C:\COMM). Naturally, GTCTL
must be located within your systems' PATH or in the directory which
contains the other GT files.
Release 5.0 is a major enhancement to GTCTL. It is necessary that you
read the enclosed WHATSNEW.CTL text file to appreciate all that has been
added or changed with this release.
2
Change History
Release 5.2 08/15/87 Added date and time (automatically) when
creating new message or user records. Added
limit to 'delete inactive user' function.
Release 5.1 08/14/87 Corrected bug that resulted in currnt date
being used in revised FILES.BBS entries.
Release 5.0 08/13/87 Added Edit message function (via QEDIT).
Added ability to Copy message along with
Move message. Now shows number of users
per message area at startup. QEDIT may now
also be used to edit FILES.BBS files. You may
now edit message TOPIC as well as text. You may
change (quite important, actually) change the
format of your FILES.BBS files in order to use
GT1222 and subsequent releases so a new convert
function is included to assist you. Move/Copy
of a file now obtains descriptions from the
source FILES.BBS file but allows you to change
them. The current date is put in FILES.BBS rather
than the date the file was created/modified.
Backup/ARC function dramatically enhanced. No
longer limits to number of messages it can handle,
you may specify a default output path for ARCed
files, all Netmail directories are included. New
Netmail message bases are supported. It should no
longer be possible to scramble messages!!! This
turned out not to be a fault of GTCTL, but the
result of operator error (usually uninformed of
the problems caused by a mismatch in number of
messages versus message headers not marked with
the 'deleted' flag) or a bug in GT PowerComm that
allowed messages to be created with headers marked
'deleted'. A new report is included to show the
contents of a message base by 'Thread'. If you
edit a message header and mark it deleted you are
asked if you want the message text erased. A user
validation aid has been included that allows the
Sysop to edit all user records based on access
level. And, a few bugs were fixed.
3
GTCTL - Operations
When you start GTCTL (by simply typing: GTCTL) it will present you with
four or five options. Four provide the ability to exit the program or to
direct program output to your printer, display device or a file. You
will be presented with this same screen after each function you select
has completed. The default, shown in brackets, is to direct output to
the display device. You should know that the display will always pause
after each screen has filled in order to allow you to read what is
displayed. In the case of printed output, if a report extends beyond a
page there will be a form feed issued after a message is printed at the
bottom of the page indicating that the report is continued on the next
page. The report does not pause if printed.
The fifth option, if present, allows you to select a different message
data base as the default for all subsequent operations.
Once an output device is selected you are presented with a menu that
allows you the following choices:
0 - Exit to Output selection Menu
1 - Message Summary Report
2 - Message Control File Report(s)
3 - User/Mail Control File Report(s)
4 - Scan/Delete/Ban/Add and Update User(s)
5 - Renumber messages
6 - Sort User/Mail Control file
7 - Delete inactive users
8 - Delete specified messages
9 - Scan/Update/Add/Move/Copy/Edit Archive message header(s)
A - ASCII capture file converter
B - Backup/Archive critical files
C - Condense message control file
F - Create/Update FILES.BBS or WHATS.NEW file
S - Host mode Status Charts
V - Validation aid - Authorization level changes
The default is 0; to return to the Main Menu.
Option 1 provides a Summary of the contents of your Message Data Base.
For every user of the system that has either a currently active message
that he has sent or which is addressed to him, there will be a listing
which includes his name and a list of the messages numbers that relate
to him that are in the file. The numbers that are enclosed in brackets
are addressed to him while the others are messages he has sent.
Option 2 prepares a complete report of the message control file and the
message data base. Each entry on the report consists of the message
number, the sender and receiver names, the time and date it was sent,
the topic of the message, and flags that show whether the message was
private and/or received, up to the first three reply numbers for that
message, and the message number that this message is a reply to, if any.
Finally, the actual message is displayed, if found, or a warning that
that particular message could not be found in the data base.
Option 3 prepares a report that includes the contents of the User/Mail
control file. This file contains the names of all users who have logged
onto the system while it has been in Host mode. Besides the user's
name, the file contains information such as the message number he has
last read, the date and time of his last call, the number of calls he
has made to your system, whether he has elected 'Expert' mode, whether
he has been Banned from accessing your system, and whether he wants the
More? display control function. Additional information may be expected
to reside in this control file in the future.
Option 4 is used to specify a list of users that are to be deleted or
banned from the system. Banning a user retains the user name in the
User/Mail control file and disallows the use of that user name to gain
access to your system. NOTE: this obviously does not prevent him from
adopting another name and using the same password to log on with! It is
used primarily to prevent the use of a set of names or handles on your
system that you might find offensive and to discourage a casual but
undesirable user from getting into the system. Similarly, deleting a
user name merely forces the system to recognize that user's next call to
be his FIRST one. It results in the NEWUSER bulletin being presented
the next time that user name is employed. Sub function 3 allows you to
reverse the prior deletion or banning of a user thus you will no longer
have to delete it if you want to un-ban that name. You are asked
if you want to delete or ban the list you next enter. The format of
input is simply to type the user names with a blank between (it is not
case sensitive) and, if there are more than one such name, to put a
comma between names.
Option 5 will do two things at once. First, it will eliminate all
deleted records from the file and second, it will renumber all active
messages starting with the number one. Obviously, all control file
references to message numbers are also renumbered so that, for example,
the last message read for each user will remain consistent with the
resulting message numbers in the file.
Option 6 will sort the User/Mail file in order to get it into user name
order. As each new user calls into the system his name is appended to
the file. The sort function allows you to sequence the file
alphabetically by either the user's first or last name or numerically in
descending order of date last called.
Option 7 allows you to delete inactive users of your system. 'Inactive'
means that the caller has not called your board within a specified time
period (for example, within two months). You specify the time period at
the time you select this option.
Option 8 provides you the ability to eliminate messages from the message
data base and GTMESSAG.CTL header file. You may do so by selecting
either: All Private received mail, All Public received mail, All mail
that has been in the file longer than a certain specified number of
days, or via a specified of message numbers.
5
Option 9 provides you the tools necessary to edit your Message Control
file. With this option you may edit existing entries, delete such an
entry, move messages from one message base to another, create new
entries, and ARCHIVE a set of messages. Please note, the archive
function REQUIRES that you have PKARC in your DOS path and after this
function is completed the archived messages will be deleted and the
message headers marked 'deleted' (the ARC file will be in GT directory).
Irwin FIP and Compaq TAPE commands are supported. Edit of a message is
supported only if you have a copy of QEDIT on your system.
-> NOTE: It is very important that you realize that marking a message
-> header 'Deleted' is NOT the same as deleting the actual message text
-> file. If you should fail to erase text files that have been marked as
-> 'deleted' then subsequently invoke the re-number function of this
-> program your message base will be irretrievably scrambled as a result!
Option A allows you to convert a captured text file that contains 'monitor
mode' escape sequences in it to full ANSI files. This is particularly
useful if, for example, you wish to capture a color/graphic menu and see
what it looks like later.
Option B provides the user with a convenient way to backup or archive all
critical Host mode files (GTMAIL.CTL, GTMESSAG.CTL, GTMDIR.BBS,
GTDIR.BBS, GT.LOG and all messages).
It assumes the existence in your system of either a standard BACKUP
program or ARC or PKARC and that these are available via the PATH by DOS.
You may send the output to floppy disk or to a default directory whether
you choose the BACKUP or ARC methods. The author strongly suggests that
you employ this function at least once a day!
Note, it is YOUR responsibility to insure that your output device has
sufficient capacity should you elect any of the ARC functions. The
program runs with interrupts disabled during Backup/ARC to insure that
it runs to completion. Should your device (particularly a floppy) get
full you will have no ability to recover (but no damage occurs).
A word about naming conventions used should you elect to use the ARC
method provided. GTCTL will send all critical files found in the GT
directory to an ARC file with the name of mm-dd-yy.ARC. If that file
already exists it will be updated. Then, using the GTMDIR.BBS file (if
it exists), the program will create seperate ARC files for each message
directory found listed in that file and will use the folling name:
mmddyynn.ARC where nn is the relative sequence number of the directory
as listed in GTMDIR.BBS.
In other words, if you have a message directory listed in your GTMDIR.BBS
file called C:\GAMES and it is the third directory listed in that file,
then GTCTL will create an ARC file called mmddyy03.ARC and will put that
directories' control files into that ARC file. Messages will be placed
into similarly named files except that the .ARC extension is not used.
Instead, messages are ARCed in groups of 100 and placed into archives that
have file names that are numeric and reflective of the set of messages
contained. (ie, .000 is the ARC file that contains messages 1-99, .001
contains messages 100-199, etc.) Note that these files are archives even
though they do not end with .ARC.
5.1
Option C allows you to condense the size of your message base control
file (GTMESSAG.CTL). If there are deleted message headers at the very
beginning of the file or at the end of it, this function eliminates the
space taken by these headers and moves all other headers forward into
the file. Simultaneously, a new 'offset' is recorded into header record
number 0 so that re-numbering of messages is not required. This function
is particularly valuable to Sysops that wish not to do renumbering of
messages and maintain a perpetually incrementing message number.
Option F provides the functions necessary to maintain the FILES.BBS files
and to move files from one file directory to another along with their
descriptions (alphabetical order being maintained). The WHATS.NEW files
are also created with this selection upon demand. These are listings of
all files in the directory sorted by date rather than by file name.
Option S provides the user the ability to print or display charts showing
the Host Mode Status of GT PowerComm during the current month. There are
currently three charts available and examples are included in this DOC.
The status reports that are available via Option S are:
Telephone Usage Hours by Day - Shows the time your telephone has been
'Off-hook' in either Answer or Originate mode. It also shows
the running average 'Off-hook' time and number of calls per
day.
Calls-per-hour by Time and Day - Shows the number of calls received
or placed for every hour of every day of the month along with
the total calls per day and a summary of calls by baud rate.
The summary also shows average connect time by baud rate and
overall average connect time as well as effective system baud
rate (average of averages).
Calls per hour month-to-date - Shows relative activity of your board
by hour of the day and average calls received during that
hour M-T-D. It also indicated the average number of calls by
hour of day. Users can use this chart to plan the best time to
call your board (highest odds of getting a connect).
Option V is a validation aid. Normally, you allow new users to enter
your system with a relatively low authorization level ('Z', for example),
and once you have validated these users you will want to change their
autorization levels. While GTCTL will allow you to glaobally change any
authorization level to any other, this function allows you to see each
user at the specified level (Z) and to decide if that user's level should
be changed and, if so, to specify any other level to be assigned.
5.2
GTCTL - Additional notes
GTCTL will (without announcing it) begin by looking for your GTDIR.BBS
file. It then will look into each of the directories specified in that
file and insure that there is a FILES.BBS file. If not, it will create
that file for you and the contents of the created file will be a single
text line that says: "No descriptions currently available."
Finally, and without notification to the user, Option 3 will shrink
the GTMAIL.CTL file if it is possible to do so (because of deleted users
in the file). It will do this, however, only when you list the entire
file (using option 0 when asked the starting user number).
The GTMESSAGE.CTL file is shrunk automatically only at the time of renumbering
of messages because of deletions found therein or via the Condense Option
previously discussed.
Care has been taken to minimize the risk of corrupting files by keeping
them 'closed' until the last possible moment before they are updated,
and then they are immediately closed again.
* N O T I C E *
Given the care and design of this program towards protecting the
integrity of your messages and control files, it would be reasonable to
presume that these files are important to the operation of your Host
system. They are. Therefore, it cannot be overemphasized that a daily
backup (or complete ARCing) is essential to minimize the effect of any
corruption of those files resulting from any cause or reason. That is
why the function has been created for you, but the author cannot force
you to use it. Be advised that there is always the possibility of file
corruption; from power outages, to errors in the logic of programs such
as this one. Your use of this program is evidence of your agreement to
assume the entirety of that risk and that you will not hold the author
or his associates or distributors liable in any way should there be a
loss of data from its use.
* N O T I C E *
6
Telephone Usage Hours by Day
For the month of July as of 8/01/87 @ 1:55
24|
23|
22|
21| A A
20|---------------------------A---------A-------A-A---A----------
19| A A A A A A A A
18| A A A A A A A A A A A A A A
17| A A A A A A A A A A A A A A A A A A
16|*****A***************A*A***A*A*A***A*A*A*A*A*A*A*A*A*A*A*A*A*A
H 15|-----A-A---------A---A-A---A-A-A-A-A-A-A-A-A-A-A-A-A-A-A-A-A-A
O 14| A A A A A A A A A A A A A A A A A A A A A A A A
U 13| A A A A A A A A A A A A A A A A A A A A A A A A A A A
R 12| A A A A A A A A A A A A A A A A A A A A A A A A A A A A A A
S 11| A A A A A A A A A A A A A A A A A A A A A A A A A A A A A A A
10|-A-A-A-A-A-A-A-A-A-A-A-A-A-A-A-A-A-A-A-A-A-A-A-A-A-A-A-A-A-A-A
9| A A A A A A A A A A A A A A A A A A A A A A A A A A A A A A A
8| A A A A A A A A A A A A A A A A A A A A A A A A A A A A A A A
7| A A A A A A A A A A A A A A A A A A A A A A A A A A A A A A A
6| A A A A A A A A A A A A A A A A A A A A A A A A A A A A A A A
5|-A-A-A-A-A-A-A-A-A-A-A-A-A-A-A-A-A-A-A-A-A-A-A-A-A-A-A-A-A-A-A
4| A A A A A A A A A A O A A O A A A A A A A A A A A A A A A A A
3| O A O O A A A A A O O A A O A A O A A O O A O A A A A A A A A
2| O O O O A A O O O O O O A O O O O O A O O A O A A A O A O A O
1| O O O O A O O O O O O O O O O O O O A O O O O A O O O A O O O
==============================================================
-|-|-|-|05-|-|-|-|10-|-|-|-|15-|-|-|-|20-|-|-|-|25-|-|-|-|30-|
O = Originate A = Answer * = Average
Calls-per-hour by Time and Day
For the month of July as of 8/01/87 @ 1:55
00:00| 2 1 2-- 3---- 1 1 2-- 2 1 1 1 2 1 2 2---- 2 4 1-- 5-- 5 1 2 1 45
01:00| 1 1 6 2 5 1 2 2 5 1 3 2 3 5 1 2 2 5 2 3 1 1 4 3 2 1 66
02:00| 1 1 3 2 2 2 3 3 3 2 1 2 2 3 1 5 1 1 2 6 1 4 1 3 2 57
03:00| 1 1 1 1 1 1 1 1 3 2 3 2 3 2 3 1 3 1 3 1 5 4 1 2 1 1 1 50
04:00| 2 1 2 1 1 2 1 2 3 3 2 2 5 2 1 2 1 6 1 1 4 2 2 2 2 1 54
05:00| 2 1 2 1 1 1 1-- 1 1 1 2 3 1 3 5 1 4 3 2 1 1 3 2 1 3-- 5 3 2 1 58
06:00| 3 1 1 1 1 1 1 1 2 4 1 4 2 3 2 5 2 3 1 1 1 2 3 2 4 52
07:00| 4 3 2 1 1 1 1 3 2 3 2 3 4 2 8 1 1 1 5 3 5 3 2 3 1 4 3 3 75
08:00| 2 1 3 2 1 1 2 2 1 3 6 3 6 6 3 3 6 2 1 4 8 4 2 3 4 2 2 5 1 1 90
09:00| 2 1 1 2 1 3 1 1 3 2 2 1 4 3 3 1 2 3 2 2 3 2 4 1 2 4 2 4 3 65
10:00| 3 3-- 2---- 5 1 2 3 1 3 1 2-- 2 4 4 3 2 3---- 3 2 3 1 3 2-- 2 60
T 11:00| 1 1 2 3 4 1 3 2 1 3 1 2 4 3 2 2 1 5 2 3 2 1 2 1 1 1 3 2 3 62 C
I 12:00| 1 1 4 2 2 2 1 4 1 2 3 4 3 1 3 5 3 2 2 1 3 4 2 1 3 2 4 1 1 1 69 A
M 13:00| 2 4 2 1 2 3 2 2 3 2 3 3 2 2 1 2 2 1 4 2 1 3 1 2 4 4 1 4 65 L
E 14:00| 1 2 1 5 1 2 2 4 2 1 2 3 5 1 1 4 5 1 1 3 3 3 1 2 3 4 2 4 2 2 73 L
15:00| 2 2 1 1 4 1 2 3 3-- 4 2-- 4 2 2 2 1 1 2 2 1 4 4 2 1 2 1 5 3 5 69 S
16:00| 1 3 2 3 3 2 1 3 3 2 2 2 2 1 1 2 4 2 2 2 3 1 1 1 3 1 3 56
17:00| 2 2 2 1 3 1 1 6 1 2 1 2 1 3 1 1 4 3 1 2 2 1 4 3 6 1 2 59
18:00| 4 3 1 3 1 1 3 5 3 2 6 2 3 4 5 1 2 3 2 1 6 4 2 2 2 1 4 76
19:00| 1 1 5 1 2 3 1 3 2 3 2 1 2 4 2 5 3 2 3 3 4 2 2 2 1 4 3 67
20:00| 1 1 1 2 2 1 2 2 4 4 5 3 6-- 1 1 1 1 1 2 6 4 1 2-- 4 2 3 6 3 2 74
21:00| 1 1 2 1 3 3 1 3 5 5 1 3 4 2 5 1 3 3 9 2 5 1 2 2 2 5 1 2 78
22:00| 3 3 1 1 3 2 2 4 7 3 2 2 6 6 2 1 2 3 4 2 1 3 1 3 2 5 2 3 2 81
23:00| 3 5 3 2 3 3 3 3 1 1 1 2 4 1 1 1 1 1 1 3 5 4 1 3 1 1 4 1 3 66
====================================================================
-|-|-|-|05-|-|-|-|10-|-|-|-|15-|-|-|-|20-|-|-|-|25-|-|-|-|30-| 1567
3 4 3 5 4 3 3 3 3 6 5 5 4 6 5 6 5 5 4 5 5 6 6 5 4 6 4 7 6 3 5
8 0 8 0 0 8 9 2 8 3 9 3 6 1 2 6 0 0 8 4 1 8 6 1 1 5 1 2 5 9 3
CALLS
429 @ 2400 baud average duration = 16.6 minutes
920 @ 1200 baud average duration = 23.2 minutes
16 @ 300 baud average duration = 16.3 minutes
88 @ Local Test average duration = 12.1 minutes
=================================================
1453 1490 <-- Average --> 20.5
Total calls excludes any of duration less than 15 seconds
Calls by hour month-to-date
For the month of July as of 8/01/87 @ 1:56
00:00|********************** | 45
01:00|********************************* 66
02:00|**************************** | 57
03:00|************************* | 50
04:00|*************************** | 54
05:00|***************************** | 58
06:00|************************** | 52
07:00|************************************* 75
08:00|********************************************* 90
09:00|********************************| 65
10:00|****************************** | 60
T 11:00|******************************* | 62 C
I 12:00|********************************** 69 A
M 13:00|********************************| 65 L
E 14:00|************************************ 73 L
15:00|********************************** 69 S
16:00|**************************** | 56
17:00|***************************** | 59
18:00|************************************** 76
19:00|********************************* 67
20:00|************************************* 74
21:00|*************************************** 78
22:00|**************************************** 81
23:00|********************************* 66
====================================================================
-|-|-|-|20-|-|-|-|40-|-|-|-|60-|-|-|-|80-|-|-|-|00-|-|-|-|20 Avg= 66
(Sample Message base thread report)
C:\GT_HINTS\ .. threads ..
===============================================================================
1 James Davis ----------------------------------- POWER-LOSS-PROTECTED HOST
2 James Davis ----------------------------------- POWER-LOSS-PROTECTED MODE
3 James Davis ----------------------------------- GT under DESQview
13 Brad Grivas ................................ DESQVIEW
14 Reginald Hirsch ......................... DESQVIEW
15 Reginald Hirsch ...................... PATIENTS
4 James Davis ----------------------------------- PROTOCOL PERFORMANCE
5 James Davis ----------------------------------- PCP COMMANDS
6 Robert Duncan --------------------------------- HELP
7 Raymond Wood ---------------------------------- GT_HINTS
10 James Davis ................................ HINTS
8 Raymond Wood ---------------------------------- AUTO30_1.ARC
11 James Davis ................................ AUTO30...
9 Robert Duncan --------------------------------- UPLOADING
16 James Davis ----------------------------------- BBS SOFTWARE
17 James Davis ----------------------------------- DV VS DDOS
23 Brad Grivas ................................ DV VS DDOS
21 John Crenshaw --------------------------------- GT 1222
22 James Davis ................................ BETA
24 James Davis ----------------------------------- SCRIPTS
25 Steven Byrnes .............................. SCRIPTS
27 Bruce Aldrich .............................. ONLINE & FLUSH
28 James Davis ............................. FLUSH
26 James Davis ----------------------------------- MESSAGE BASE SCRAMBLING
29 Boyd Fowler ----------------------------------- CALL WATING
Name conventions used by Backup/ARC:
Default message base path: C:\COMM
Directories: C:\COMM
C:\COMM\GTMSGS
C:\COMM\GENERAL
C:\COMM\GENERAL\GTMSGS
C:\COMM\PRIVATE
C:\COMM\PRIVATE\GTMSGS
GTMDIR.BBS contents:
... C:\COMM default message base
... C:\COMM\GENERAL General purpose messages
... C:\COMM\PRIVATE Private messages
Output files: C:\COMM\08-12-87.ARC
Contains all GT BBS and CBS files, the log, GT.CNF, GT.DIR,
and, because it (C:\COMM) is the default message base, both
CTL files.
C:\COMM\08-12-87.000
Contains all messages from default message base with filenames
that are between 00001.MSG and 00099.MSG.
C:\COMM\08-12-87.001
Contains all messages from default message base with filenames
that are between 00100.MSG and 00199.MSG.
C:\COMM\08128702.ARC
Contains all .BBS and .CBS and .CTL files from C:\COMM\GENERAL
as this is the second (note the '02' in file name) named message
directory in your GTMDIR.BBS file.
C:\COMM\08128702.000
Contains all messages from C:\COMM\GENERAL\GTMSGS that have
filenames from 00001.MSG through 00099.MSG.
etc.
Note, had the default message base (as defined in your GT.CNF file) been other
than C:\COMM then that message base would be in the 08-12-87 files and there
would have been a 08128701.ARC file. Also, the output filenames shown here
assume that you have not specified some other default output path name.
[ REGISTRATION FORM ]
[ ]
[ ]
[ DATE:__________ TO: P & M Software Co. ]
[ 9350 Country Creek #30 ]
[ Houston, Tx 77036 ]
[ ]
[ ]
[ FROM: NAME:________________________________________ ]
[ ]
[ ADDRESS:________________________________________ ]
[ ]
[ ________________________________________ ]
[ ]
[ ________________________________________ ]
[ ]
[ ]
[ CHECK 1 ITEM: ]
[ ]
[ 1. ___ INITIAL REGISTRATION OF "GT PowerComm" (SUGGEST $50). ]
[ ]
[ 2. ___ UPGRADE TO NEW VERSION OF "GT PowerComm" (SUGGEST $10). ]
[ IF YOU ARE ALREADY A REGISTERED USER, YOU CAN USE THIS ]
[ OPTION TO OBTAIN AN OFFICIALLY REGISTERED COPY. ]
[ ]
[ PLEASE SUPPLY THE SERIAL NUMBER AND VERSION FROM THE ]
[ COPY OF THE PROGRAM YOU ARE CURRENTLY USING. USE THE ]
[ ALT-J COMMAND TO OBTAIN THIS INFORMATION. ]
[ ]
[ SERIAL # _________ VERSION # ___________ ]
[ ]
[ ]
[ PLEASE INDICATE AMOUNT ENCLOSED ]
[ -------------------------------------- ]
[ ]
[ Contribution Amount: __________ ]
[ ]
[ TX residents add sales tax: __________ ]
[ ]
[ TOTAL ENCLOSED: __________ ]
[ ]
[ Sales Tax Note ]
[ -------------- ]
[ To compute the proper sales tax you should include 5.25% for the ]
[ TX state tax, Houston residents should add 1% for the city sales ]
[ tax, and MTA residents should add an amount equal to their local ]
[ MTA rate. In Houston and Dallas, the MTA rate is 1%. ]
[ ]
[ PLEASE DO NOT SEND CASH, SEND CHECK OR MONEY ORDER. YOUR REQUEST ]
[ WILL BE FILLED PROMPTLY UPON RECEIPT. ]
------------------------------------------------------------------------